User datagram protocol (udp) packet migration in a virtual machine (vm) migration

ABSTRACT

Embodiments of the invention relate to receiving, by a first processor comprising a processing device, an indication that a migration of a virtual machine from the first processor to a second processor is to occur. The first processor transmits user datagram protocol (UDP) packets intended for the virtual machine to the second processor based on the indication. A signal is transmitted to the virtual machine to enter an offline state, wherein the offline states comprises a transfer of at least one of a central processing unit (CPU) state and a memory state, and wherein the virtual machine is configured to halt a processing of the UDP packets in response to receiving the signal. The virtual machine is reactivated once the migration of the virtual machine from the first processor to the second processor is complete. The virtual machine is instructed to resume the processing of the UDP packets.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.13/690,135 (Dow et al.), filed on Nov. 30, 2012, and a continuation ofU.S. application Ser. No. 14/090,523 (Dow et al.), filed on Nov. 26,2013, which is herein incorporated by reference in its entirety.

BACKGROUND

The present invention relates to management of virtual machines (VMs),and more specifically, to a user datagram protocol (UDP) packetmigration in a virtual machine (VM) migration.

Providers of cloud computing have the competing tasks of providingdesired performance for consumers or end users while also efficientlyallocating the resources used to provide services to consumers. Theresources may be dynamically allocated by the provider to help achievethese goals. Accordingly, a hardware platform may host a plurality ofvirtual machines, wherein each virtual machine corresponds to aconsumer. Efficient use of the hardware platform resources dictates thatthe provider place as many virtual machines on the platform as possiblewithout compromising the consumer's use of the virtual machine andexperience. It may be desirable to move or migrate a virtual machinefrom one hardware platform to another to ensure that the customer is notadversely affected by changes in resources for the virtual machines.

Environments based on the Transmission Control Protocol (TCP) are ableto continue working through a migration because TCP windows aregenerally longer than the “offline” portion of a virtual machinemigration process that suspends all input/output (I/O) and guestprocessing while a final processing state and other miscellaneous dataare sent to a remote host where execution is subsequently resumed.Another network protocol is the user datagram protocol (UDP) which doesnot include guarantees regarding retry or ordering as compared to TCP.

SUMMARY

An embodiment is directed to a method comprising receiving, by a firstprocessor comprising a processing device, an indication that a migrationof a virtual machine from the first processor to a second processor isto occur. The method further comprises transmitting, by the firstprocessor, user datagram protocol (UDP) packets intended for the virtualmachine to the second processor based on the indication. The methodfurther comprises transmitting a signal to the virtual machine to enteran offline state, wherein the offline states comprises a transfer of atleast one of a central processing unit (CPU) state and a memory state,and wherein the virtual machine is configured to halt a processing ofthe UDP packets in response to receiving the signal. The method furthercomprises reactivating the virtual machine once the migration of thevirtual machine from the first processor to the second processor iscomplete. The method further comprises instructing the virtual machineto resume the processing of the UDP packets.

An embodiment is directed to an apparatus comprising at least oneprocessing device, and memory having instructions stored thereon. Theinstructions, when executed by the at least one processing device, causethe apparatus to receive an indication that a migration of a virtualmachine from the apparatus to a processor is to occur. The instructions,when executed by the at least one processing device, cause the apparatusto transmit user datagram protocol (UDP) packets intended for thevirtual machine to the processor based on the indication. Theinstructions, when executed by the at least one processing device, causethe apparatus to transmit a signal to the virtual machine to enter anoffline state, wherein the offline states comprises a transfer of atleast one of a central processing unit (CPU) state and a memory stateassociated with the virtual machine, and wherein the virtual machine isconfigured to halt a processing of the UDP packets in response toreceiving the signal. The instructions, when executed by the at leastone processing device, cause the apparatus to receive a second signalindicating that the migration of the virtual machine from the apparatusto the processor is complete. The instructions, when executed by the atleast one processing device, cause the apparatus to instruct the virtualmachine to resume the processing of the UDP packets based on the secondsignal.

An embodiment is directed to a computer program product comprising acomputer readable storage medium having computer readable program codeembodied therewith. The computer readable program code comprisescomputer readable program code configured for receiving, by a firsthypervisor associated with a first processor, an indication that amigration of a virtual machine from the first processor to a secondprocessor is to occur. The computer readable program code is configuredfor causing, by the first hypervisor, the first processor to transmituser datagram protocol (UDP) packets intended for the virtual machine toa second hypervisor associated with the second processor based on theindication. The computer readable program code is configured forcausing, by the first hypervisor, the first processor to transmit asignal to the virtual machine to enter an offline state, wherein theoffline states comprises a transfer of at least one of a centralprocessing unit (CPU) state and a memory state, and wherein the virtualmachine is configured to halt a processing of the UDP packets inresponse to receiving the signal. The computer readable program code isconfigured for reactivating the virtual machine once the migration ofthe virtual machine from the first processor to the second processor iscomplete. The computer readable program code is configured forinstructing the virtual machine to resume the processing of the UDPpackets.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The foregoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention;

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention;

FIG. 4 illustrates a computing system for migrating a virtual machine inaccordance with an embodiment; and

FIG. 5 illustrates a flow chart of a process for providing data packetsto a migrating virtual machine in accordance with an embodiment.

DETAILED DESCRIPTION

Embodiments described herein are directed to virtual machine (VM)migration in computing environments that utilize the user datagramprotocol (UDP) as a basis for transmitting or receiving data. In anembodiment, a hypervisor buffers UDP packets intended for a VM that hasbeen placed in an offline state during a migration of the VM from afirst processor to a second processor. When migration of the VM iscomplete, the hypervisor forwards the buffered UDP packets to ahypervisor executing on the second processor for processing by themigrated VM. In this manner, UDP packets are not lost during, or as aresult of, the migration.

In an embodiment a signal is sent to a hypervisor indicating that a VMis about to be migrated. Based on receiving the signal, the hypervisorperforms any migration that can be performed online where the VM remainsresponsive to the outside world. At the point in time when thehypervisor or VM determines that the VM must go into an offline phase ofthe migration (e.g., a phase where the VM is not performing computationand is having a critical execution state such as a central processingunit or “CPU” state and or a memory state being transferred), thehypervisor buffers inbound UDP packets intended for the migrating VM. Inan embodiment, before entering the offline phase of migration, thehypervisor sends a signal (e.g., inband or out of band) to the VM undermigration to halt processing of UDP packets. When the migration hascompleted, the hypervisor then retransmits the UDP packets intended forthe VM to a new hypervisor executing the migrated VM. The VM is thenreactivated on the remote side, where it resumes execution and theretransmitted UDP packets are delivered. In an embodiment where the VMhad been instructed to buffer UDP packets and not process them, thehypervisor instructs the VM (e.g., using an inband or out of bandsignal) to normally operate on UDP packets after having optionallyreordered its current buffer before processing. The UDP packets may bebuffered in kernel or userspace memory in the guest or hypervisor.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed (e.g., any client-server model).

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples, include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security (not shown) provides identity verificationfor cloud consumers and tasks, as well as protection for data and otherresources. User portal provides access to the cloud computingenvironment for consumers and system administrators. Service levelmanagement provides cloud computing resource allocation and managementsuch that required service levels are met. Service Level Agreement (SLA)planning and fulfillment provide pre-arrangement for, and procurementof, cloud computing resources for which a future requirement isanticipated in accordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and a mobile desktop for mobile devices (e.g., 54A, 54C, and54N, as well as mobile nodes 10 in cloud computing environment 50)accessing the cloud computing services.

In one embodiment, one or both of the hardware and software layer 60 andthe virtualization layer 62 may include edge components, such as a webserver front end and image cache, as well as an image library store,e.g., in a high-performance RAID storage area network (SAN). In anexemplary embodiment, an application, such as a virtual machinemonitoring application 70 in the virtualization layer 62, may implementa process or method for migrating one or more virtual machines; however,it will be understood that the application 70 may be implemented in anylayer. In some embodiments, the application 70 may buffer packetsintended for a migrating virtual machine and may deliver the bufferedpackets once the migration is complete.

Turning now to FIG. 4, a computing system or environment 400 inaccordance with an embodiment is shown. The system 400 may be indicativeof a cluster or work group.

The system 400 includes three devices, device 1 402, device 2 404, anddevice 3 406. The devices 402, 404, and 406 may be configured tocommunicate with one another. For example, the devices 402, 404, and 406may be configured to communicate with one another over wired or wirelessconnections. While the system 400 is shown as including three devices,in some embodiments more or fewer than three devices may be included. Insome embodiments, one or more of the devices 402, 404, and 406 mayinclude, or be associated with, one or more of the entities describedabove in connection with FIG. 1.

One or more of the devices 402, 404, and 406 may include one or morecomponents. For example, the device 402 is shown in FIG. 4 as includinga processor 408 and memory 410. The memory 410 may be configured tostore data or information. The memory 410 may have instructions storedthereon that, when executed by the processor 408, cause the device 402to perform one or more methodological acts, such as those describedherein. In some embodiments, the device 402 may include more than oneprocessor 408. The device 402 may include additional components notshown in FIG. 4. For example, the device 402 may include a transceiverto facilitate communications with the devices 404 and 406.

The device 402 is shown in FIG. 4 as being coupled to the device 404 viaa link 412. The device 404 is shown in FIG. 4 as being coupled to thedevice 406 via a link 414. The device 406 is shown as being coupled tothe device 402 via a link 416. In some embodiments, one or more of thelinks may be optional. For example, if link 416 is omitted, then thedevice 402 and the device 406 might not communicate with one another, ormay communicate with one another via the device 404 serving as anintermediary or router of communications between the devices 402 and406.

One or more of the links 412, 414, and 416 may correspond to atransmission path for a packet (e.g., a UDP packet). The links 412, 414,and 416 may be used to share or transfer information or data from afirst device to a second device. Such transfer may take place inresponse to, or based on, a machine migration (e.g., virtual machinemigration).

In some embodiments, one or more of the devices or machines 402, 404,and 406 may include a hypervisor. For example, as shown in FIG. 4, thedevice 404 includes a hypervisor 418, and the device 406 includes ahypervisor 420.

Assuming a migration, such as a migration of data and/or processingstate associated with a virtual machine (VM) or guest 422, from thedevice 404 to the device 406, the hypervisor 418 may receive a signalindicating that the VM 422 is about to be migrated. The hypervisor 418may opt to perform any migration that may be considered to be “online”where the VM 422 remains responsive to the outside world.

At a time when the hypervisor 418 or VM 422 determines that the VM 422must go into an offline phase of the migration, where the offline phaseof the migration may correspond to the VM 422 not performingcomputations and/or having an execution state such as a CPU state ormemory state transferred, the hypervisor 418 may buffer inbound packets(e.g., UDP packets) intended for the VM 422. In some embodiments, thehypervisor 418 may send an in-band or out-of-band signal to the VM 422under migration to halt processing of packets (e.g., UDP packets) beforeentry of the offline phase.

In some embodiments, an ordering of packets may be provided. Forexample, if packets are buffered on behalf of the migrating VM 422, thepackets may be buffered in order, such that when the VM 422 resumesoperation or returns online following the migration, the packets arepresented to the VM 422 in sequence. In this manner, efficiency may beenhanced by minimizing or eliminating the amount of packet re-orderingthat needs to be undertaken by the VM 422.

When migration has completed, the hypervisor 418 may retransmit thebuffered packets intended for the VM 422 to the hypervisor 420 fordelivery. Alternatively, the packets may be provided to the hypervisor420 as the migration of the VM 422 from the device 404 to the device 406is occurring.

The VM 422 may be reactivated on the remote machine (e.g., device 406),whereby the VM 422 may resume execution and the packets that werebuffered (if any) may be provided to the VM 422 for processing. If theVM 422 had been instructed to not process packets prior to entry of theoffline phase, the hypervisor 418 may signal or instruct (in-band orout-of-band) the hypervisor 420 and/or the VM 422 to normally operate onsuch packets, potentially after having reordered such packets.

In some embodiments, packets may be buffered in a kernel or user-spacememory in a VM/guest (e.g., VM/guest 422) or a hypervisor (e.g.,hypervisor 418).

Turning now to FIG. 5, a flow chart of an exemplary method 500 is shown.The method 500 may be executed in connection with one or more systems,devices, or components, such as those described herein. In someembodiments, the method 500 may be executed in connection with theapplication 70 of FIG. 3. The method 500 may be executed in order tomigrate a VM or guest from a first location (e.g., a first device ormachine) to a second location (e.g., a second device or machine).

In block 502, a migration indication may be received. The migrationindication may be received by, e.g., a hypervisor associated with thefirst location. The migration indication may be received for any numberof reasons. For example, a determination may be made that the secondlocation provides for more reliable or less expensive computingresources, for purposes of load balancing, etc.

In block 504, the hypervisor associated with the first location mayperform any migration considered online where the VM remains responsiveto the outside world or one or more inputs, optionally based on theindication of block 502.

In block 506, the hypervisor associated with the first location mayplace the VM in an offline state. As part of block 506, the hypervisorassociated with the first location may buffer inbound packets intendedfor the VM. As part of block 506, the hypervisor associated with thefirst location may instruct the VM to halt processing of packets. Aspart of block 506, the migration of the VM may occur.

In block 508, the hypervisor associated with the first location mayforward or transmit any packets that it may have buffered as part ofblock 506. The hypervisor associated with the first location may: (1)forward the packets to the VM at the second location, or (2) may forwardthe packets to a second hypervisor associated with the second locationfor forwarding to the VM.

In block 510, the VM may be reactivated at the second location once themigration is complete. As part of block 510, the hypervisor associatedwith the first location may instruct the hypervisor associated with thesecond location or the VM to process any packets that may have beensubject of the “halt” of block 506.

The method 500 is illustrative. In some embodiments, one or more of theblocks (or a portion thereof) may be optional. In some embodiments, theblocks may execute in an order or sequence that is different from whatis shown in FIG. 5. In some embodiments, one or more additional blocksnot shown may be included.

Technical effects and benefits include increasing or enhancingresiliency of one or more computing devices, such as UDP based serverswhen running on a virtualized platform. Such servers may be operative inconnection with, e.g., the Network Time Protocol (NTP), the Dynamic HostConfiguration Protocol (DHCP), the Voice over Internet Protocol (VoIP),etc.

Aspects of the disclosure may be implemented in connection with highperformance networks, or in environments where performance trumps theneed for strict ordering of data packets. Aspects of the disclosure maybe exploited or implemented in environments where servers are subject tolarge loads (e.g., a large number of client computers and/or a largevolume of data), or where servers are migrated frequently. For example,such migration may take place in cloud data centers during loadbalancing or other migration operations that may reduce cost by movingcomputation activities to where the computation is inexpensive.

Aspects of the disclosure may be implemented in connection with, e.g.,point of sale (POS) systems, accounting systems, database systems,telephone and voice over internet protocol (VoIP) systems, etc.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiments were chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

Further, as will be appreciated by one skilled in the art, aspects ofthe present invention may be embodied as a system, method, or computerprogram product. Accordingly, aspects of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.) oran embodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, radio frequency (RF), etc., or anysuitable combination of the foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method comprising: receiving, by a firstprocessor comprising a processing device, an indication that a migrationof a virtual machine from the first processor to a second processor isto occur; transmitting, by the first processor, user datagram protocol(UDP) packets intended for the virtual machine to the second processorbased on the indication; transmitting a signal to the virtual machine toenter an offline state, wherein the offline states comprises a transferof at least one of a central processing unit (CPU) state and a memorystate, and wherein the virtual machine is configured to halt aprocessing of the UDP packets in response to receiving the signal;reactivating the virtual machine once the migration of the virtualmachine from the first processor to the second processor is complete;and instructing the virtual machine to resume the processing of the UDPpackets.
 2. The method of claim 1, further comprising: buffering, by thefirst processor, the UDP packets; and transmitting, by the firstprocessor, the buffered UDP packets to the second processor once themigration of the virtual machine to the second processor is complete. 3.The method of claim 2, further comprising: ordering, by the firstprocessor, the UDP packets, wherein the transmission of the UDP packetsto the second processor is based on the ordering of the UDP packets. 4.The method of claim 2, wherein the UDP packets are buffered in kernel oruserspace memory in at least one of a guest and a hypervisor.
 5. Themethod of claim 1, further comprising: transmitting, by the firstprocessor, the UDP packets intended for the virtual machine to thesecond processor without buffering the UDP packets at the firstprocessor.
 6. The method of claim 1, further comprising: instructing thevirtual machine to reorder the UDP packets prior to processing thepackets.